Systems and methods for processing off-network transaction messages

ABSTRACT

A computer-implemented method for applying payment services to a payment transaction over a first payment network using a payment services computer system hosted on a second payment network is provided. The method includes receiving a service request at the payment services computer system from a requestor. The service request has a first format that is readable by the second payment network. The method includes determining, at the payment services computer system, the payment services the service request is registered to receive. The method includes processing the service request by applying the registered payment services to the service request. The method includes generating, at the payment services computer system, a services response. The services response is generated based on the registered payment services and the payment transaction data. The method additionally includes transmitting the services response to at least one of the cardholder and the requestor.

BACKGROUND OF THE DISCLOSURE

The field of the invention relates generally to systems and methods forprocessing payment transactions and, more particularly, to systems andmethods for applying off-network payment services to a home paymentnetwork payment transaction, wherein the home payment network paymenttransaction originates on a first payment network and the paymentservices are provided by a computing device associated with a secondpayment network.

The payment card industry allows for issuer banks and cardholders to usepayment services, sometimes known as transaction enrichment services, inconjunction with transactions performed over a payment network. In somepayment systems, these payment services allow a cardholder, using aninterface, to register for such services.

These payment services may include, for example, predefined spendinglimits for a particular payment card. However, under these knownsystems, these payment services are only accessible for transactionsperformed over the “home” payment network. In other words, the paymentservices can only be applied to payment transactions that originate onthe payment network offering the payment services.

As more and more payment transactions are being performed on differentpayment networks, it is desirable to offer payment services fortransactions originating on payment networks other than the paymentnetwork where the transaction originated.

BRIEF DESCRIPTION OF THE DISCLOSURE

In one aspect, a computer-implemented method for applying paymentservices to a payment transaction over a first payment network using apayment services computer system hosted on a second payment network isprovided. The payment transaction is initiated by a cardholder using apayment card over the first payment network. The payment card is issuedto the cardholder by an issuer bank. The method includes receiving aservice request at the payment services computer system from a requestorwhere the requestor is the issuer bank or a home network processor. Theservice request has a first format that is readable by the secondpayment network. The service request includes payment transaction data.The method also includes determining, at the payment services computersystem, the payment services the service request is registered toreceive. The method further includes processing the service request byapplying the registered payment services to the service request. Themethod also includes generating, at the payment services computersystem, a services response. The services response is generated based,at least in part, on the registered payment services and the paymenttransaction data. The method additionally includes transmitting theservices response to at least one of the cardholder and the requestor.

In another aspect, a computer-readable storage media for applyingpayment services to a payment transaction over a first payment networkusing a payment services computer system hosted on a second paymentnetwork is provided. The payment transaction is initiated by acardholder using a payment card over the first payment network. Thepayment card is issued to the cardholder by an issuer bank. Thecomputer-readable storage media has computer-executable instructionsembodied thereon. When executed by at least one processor associatedwith a computer device coupled to a memory device, thecomputer-executable instructions cause the processor to receive aservice request from a requestor. The service request has a first formatthat is readable by the second payment network. The service request alsoincludes payment transaction data. When executed by the at least oneprocessor, the computer-executable instructions also cause the processorto determine the payment services the service request is registered toreceive. When executed by the at least one processor, thecomputer-executable instructions further causes the processor to processthe service request by applying the registered payment services to theservice request. When executed by the at least one processor, thecomputer-executable instructions additionally cause the processor togenerate, at the payment services computer system, a services responsebased at least in part on the registered payment services and thepayment transaction data. When executed by the at least one processor,the computer-executable instructions also cause the processor totransmit the services response to at least one of the cardholder and therequestor.

In a further aspect, a computer system for applying payment services toa payment transaction over a first payment network using a paymentservices computer system hosted on a second payment network is provided.The payment transaction is initiated by a cardholder using a paymentcard over the first payment network. The payment card is issued to thecardholder by an issuer bank. The computer system includes a processorand a computer-readable storage device. The computer-readable storagedevice has encoded thereon computer-executable instructions that areexecutable by the processor to perform functions. The functions includereceiving a service request at the payment services computer system froma requestor. The service request has a first format that is readable bythe second payment network. The service request also includes paymenttransaction data. The functions also include determining the paymentservices the service request is registered to receive. The functionsfurther include processing the service request by applying theregistered payment services to the service request. The functionsadditionally include generating a services response based at least inpart on the registered payment services and the payment transactiondata. The functions also include transmitting the services response toat least one of the cardholder and the requestor.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram illustrating an example multi-partypayment card industry system for enabling ordinary payment transactionsin which merchants and card issuers do not necessarily have a one-to-onerelationship.

FIG. 2 is a data flow diagram showing a payment processing environmentin accordance with one embodiment of the present disclosure.

FIG. 3 is a flowchart illustrating an example method implemented by thepayment services computer system shown in FIG. 2 for processing a homepayment network payment transaction using off-network payment services.

FIG. 4 is a simplified block diagram of an example computer systemrepresentative of the payment services platform in the paymentprocessing environment, shown in FIG. 2.

FIG. 5 is an expanded block diagram of an example embodiment of a serverarchitecture of the payment services computer system shown in FIG. 2.

FIG. 6 illustrates an example configuration of a cardholder computerdevice operated by a cardholder shown in FIGS. 4 and 5.

FIG. 7 illustrates an example configuration of the server computerdevice shown in FIGS. 4 and 5.

DETAILED DESCRIPTION OF THE DISCLOSURE

The following detailed description illustrates embodiments of theinvention by way of example and not by way of limitation. It iscontemplated that the systems and processes described herein havegeneral application to the aspect of processing payment cardtransactions. More specifically, the embodiments of the systems andmethods described herein relate generally to a payment card transactionthat is initiated over a first payment network, and a payment servicescomputer system that is associated with a second payment network,wherein the payment services computer system is configured to receive arequest from a requestor to apply payment services to the transaction,apply the payment services to the transaction, and transmit an output tothe requestor. Because this transaction is initiated on one paymentnetwork (i.e., the first payment network), and processed by the paymentservices computer system on another payment network (i.e., the secondpayment network), the transaction is sometimes referred to as anoff-network transaction. In the example embodiment, an off-networkpayment card transaction is a payment card transaction that is initiatedand processed over a payment network that is different from the paymentnetwork providing payment services to the transaction.

Described in detail herein are example embodiments of systems andmethods for applying off-network payment services to a home paymentnetwork payment transaction. The systems and methods facilitate, forexample, applying off-network payment services such as cardholderauthorization controls to an home payment network payment transaction,wherein the authorization controls are configured to identify, forexample, whether the transaction was initiated outside a geographicalregion allowed by the authorization controls. The systems and methodsdescribed herein include a payment services computer system configuredto receive a request associated with an payment transaction from a firstpayment network (i.e., a payment network that is not hosting the paymentservices) at a second payment network (i.e., a payment network that ishosting the payment services), and apply the payment services, asappropriate, to the payment transaction.

The methods and systems described herein may be implemented usingcomputer programming or engineering techniques including computersoftware, firmware, hardware or any combination or subset thereof,wherein the technical effect may be achieved by performing at least oneof the following steps: (a) receiving a service request generated by arequestor at the payment services computer system wherein the servicerequest relates to a first payment network payment card transaction andthe service request has a first format that is readable by a secondpayment network; (b) determining, at the payment services computersystem, the payment services the service request is registered toreceive; (c) processing the service request by applying the registeredpayment services to the service request; (d) generating a servicesresponse based at least in part on the registered payment services andthe payment transaction data; and (e) transmitting the service responseto at least one of the card holder and the requestor.

As used herein, an acquiring bank, or acquirer, is typically a bank atwhich a merchant holds an account. Further, an issuing bank, or issuer,is typically a bank at which a customer, or cardholder, holds anaccount. The account may be debited or charged through the use of adebit card, a credit card, or another type of payment card as describedherein.

As used herein, the terms “payment card,” “financial transaction card,”and “transaction card” refer to any suitable payment card, such as acredit card, a debit card, a prepaid card, a charge card, a membershipcard, a promotional card, a frequent flyer card, an identification card,a gift card, and/or any other device that may hold payment account data,such as mobile phones, smartphones, personal digital assistants (PDAs),key fobs, and/or computers. Each type of payment card can be used as amethod of payment for performing a transaction. In addition, cardholderaccount behavior can include but is not limited to purchases, managementactivities (e.g. balance checking), bill payments, achievement oftargets (meeting account balance goals, paying bills on time), and/orproduct registrations (e.g. mobile application downloads).

As used herein, the term “translation module” and related terms, e.g.,“translation module system,” refers to a method of converting servicerequests from a format used on the first payment network (e.g., by theissuer bank) to a format that may be read by the second payment networkand vice versa. The translation module may include, without limitation,a data layout protocol, an algorithm for mapping service requests fromthe first payment network format to the second payment network formatand vice versa, and an automated program that converts service requestsfrom the first payment network format to the second payment networkformat and vice versa.

As used herein, the term “home payment network” and related terms, e.g.,“home network,” refers to a first payment network where the cardholderoriginates payment card transactions and registers for payment services.Such home payment networks may include any payment networks capable ofusing the system and method described herein.

As used herein, the term “off-network payment network” and relatedterms, e.g., “off-network,” may refer to a second payment network thatis different from the home payment network where a payment cardtransaction is originated. As used herein, off-network payment networkis capable of receiving service requests from home payment network andproviding payment services for payment card transactions originatingwith home payment network.

As used herein, the term “network processor” and related terms, e.g.,“off-network processor” and “home network processor,” refers tocomputing device(s) associated with a payment network that may be usedto communicate data between computing devices associated with an issuerbank, a cardholder, a merchant, or an acquirer bank and communicate withcomputing device(s) that may be used to provide network services such aspayment services. Also, as used herein, the home network processor maybe configured to receive requests from an issuer bank and send firstservice requests to the translation module.

As used herein, the term “requestor” refers to the creator and sender ofa first service request based upon account registration or a paymenttransaction. The requestor may be either an issuer bank or the homenetwork processor. Also, as used herein, the requestor generates thefirst service request and uses the translation module to convert it to asecond service request.

As used herein, a processor may include any programmable systemincluding systems using microcontrollers, reduced instruction setcircuits (RISC), application specific integrated circuits (ASICs), logiccircuits, and any other circuit or processor capable of executing thefunctions described herein. The above examples are example only, andthus are not intended to limit the definition and/or meaning of the term“processor” in any way.

In one embodiment, computer-executable instructions are provided and areembodied on a non-transitory computer readable storage medium. Thecomputer-executable instructions cause a computer executing theinstructions to utilize a Structured Query Language (SQL) with a clientuser interface front-end for administration and a web interface forstandard user inputs and reports. In an example embodiment, the systemis web-enabled and is run on a business entity intranet. In analternative embodiment, the system is fully accessible by individualshaving authorized access from outside a firewall of the business-entitythrough the Internet. In a further alternative embodiment, the system isrun in a Windows® environment (Windows is a registered trademark ofMicrosoft Corporation, Redmond, Wash.). The application is flexible anddesigned to run in various different environments without compromisingany major functionality.

FIG. 1 is a schematic diagram illustrating an example multi-partypayment card industry system 20 for enabling ordinary paymenttransactions in which merchants 24 and card issuers 30 do notnecessarily have a one-to-one relationship. Embodiments described hereinmay relate to a payment card system, such as a credit card paymentsystem using the MasterCard® interchange network (MasterCard is aregistered trademark of MasterCard International Incorporated located inPurchase, N.Y.). The MasterCard interchange network is a set ofproprietary communications standards promulgated by MasterCardInternational Incorporated for the exchange of financial transactiondata and the settlement of funds between financial institutions that aremembers of MasterCard International Incorporated. In a typical paymentcard system, a financial institution called the “issuer” issues apayment card, such as a credit card, to a consumer or cardholder 22, whouses the payment card to tender payment for a purchase from a merchant24. To accept payment with the payment card, merchant 24 must normallyestablish an account with a financial institution that is part of thefinancial payment system. This financial institution is usually calledthe “merchant bank,” the “acquiring bank,” or the “acquirer.” Whencardholder 22 tenders payment for a purchase with a payment card,merchant 24 sends an authorization request message to a merchant bank 26for the amount of the purchase. The request may be performed over thetelephone, but is usually performed through the use of a point-of-saledevice, which reads cardholder's 22 account data from a magnetic stripe,a chip, or embossed characters on the payment card and communicateselectronically with the transaction processing computers of merchantbank 26. Alternatively, merchant bank 26 may authorize a third party toperform transaction processing on its behalf. In this case, thepoint-of-sale device will be configured to communicate with the thirdparty. Such a third party is usually called a “merchant processor,” an“acquiring processor,” or a “third party processor.”

Using an interchange network 28, computers of merchant bank 26 willcommunicate transaction data with computers of an issuer processor 29associated with an issuer 30. Issuer processor 29 may be a third partyprocessor authorized to perform transaction-related services on behalfof issuer 30, including payment card production services, payment cardprocessing services, fraud detection services, data delivery services,ATM driving services, transaction research, and cardholder supportservices. Issuer processor 29 may also provide interbank switchprocessing, including authorization, clearing and settlement, andvalue-added services. This enables issuer 30 to use one card processorfor all different payment card brands. In an alternative embodiment,issuer processor 29 may be associated with interchange network 28 andmay provide similar services.

Issuer 30 receives the transaction data from issuer processor 29, andthen determines whether cardholder's 22 account 32 is in good standingand whether the purchase is covered by cardholder's 22 available creditlimit. Based on these determinations, the request for authorization willbe declined or accepted. If the request is accepted, an authorizationcode is issued to merchant 24.

When a request for authorization is accepted, the available credit lineof cardholder's 22 account 32 is decreased. Normally, a charge for apayment card transaction is not posted immediately to cardholder's 22account 32 because bankcard associations, such as MasterCardInternational Incorporated®, have promulgated rules that do not allowmerchant 24 to charge, or “capture,” a transaction until goods areshipped or services are delivered. However, with respect to at leastsome debit card transactions, a charge may be posted at the time of thetransaction. When merchant 24 ships or delivers the goods or services,merchant 24 captures the transaction by, for example, appropriate dataentry procedures on the point-of-sale device. This may include bundlingof approved transactions daily for standard retail purchases. Ifcardholder 22 cancels a transaction before it is captured, a “void” isgenerated. If cardholder 22 returns goods after the transaction has beencaptured, a “credit” is generated. Interchange network 28 and/or issuer30 stores the payment card data, such as a type of merchant, amount ofpurchase, date of purchase, in a database 120 (shown in FIG. 2).

After a purchase has been made, a clearing process occurs to transferadditional transaction data related to the purchase among the parties tothe transaction, such as merchant bank 26, interchange network 28,issuer processor 29, and issuer 30. More specifically, during and/orafter the clearing process, additional data, such as a time of purchase,a merchant name, a type of merchant, purchase data, cardholder accountdata, a type of transaction, itinerary data, data regarding thepurchased item and/or service, and/or other suitable information, isassociated with a transaction and transmitted between parties to thetransaction as transaction data, and may be stored by any of the partiesto the transaction.

After a transaction is authorized and cleared, the transaction issettled among merchant 24, merchant bank 26, interchange network 28,issuer processor 29, and issuer 30. Settlement refers to the transfer offinancial data or funds among merchant's 24 account, merchant bank 26,issuer processor 29, and issuer 30 related to the transaction. Usually,transactions are captured and accumulated into a “batch,” which issettled as a group. More specifically, a transaction is typicallysettled between issuer 30 and issuer processor 29, and then betweenissuer processor 29 and interchange network 28, and then betweeninterchange network 28 and merchant bank 26, and then between merchantbank 26 and merchant 24.

FIG. 2 is a data flow diagram showing a payment processing environment100 in accordance with one embodiment of the present disclosure.Environment 100 includes a home payment network 102 where a paymenttransaction 104 or account registration 115 originates and a firstservice request 111 is sent, a transfer process 135 where first servicerequest 111 is converted to a second service request 109, and anoff-network payment network 108 where a payment services computer system107 resides.

Home payment network 102 includes a cardholder 110, an issuer 120, anacquirer 125, a merchant 130, and home network processor 112. Cardholder110 is capable of making payment transaction 104 to merchant 130.Cardholder is also capable of account registration 115 with issuer 120.Home payment network 102 is capable of communicating with off-networkpayment network 108 by sending first service request 111 associated withaccount registration 115 and/or payment transaction 104 to transferprocess 135. First service request 111 may be sent by home networkprocessor 112 or issuer 120.

Transfer process 135 is configured to allow first service request 111 tobe converted to second service request 109 that may be processed usingpayment services computer 107 at off-network payment network 108.Transfer process 135 includes converting first service request 111 intosecond service request 109 using a translation module. In the exampleembodiment, the translation module refers to a data layout protocolindicating a method of converting a first data file format associatedwith home payment network 102 (e.g., first service request 111) to asecond data file format associated with off-network payment network 108(e.g., second service request 109). In alternative embodiments, thetranslation may include, without limitation, an algorithm for mappingservice requests from the first data file format to the second data fileformat, or an automated program that converts first service request 111to second service request 109. Transfer process 135 is also configuredto send second service request 109 to an interface processor 140 atoff-network payment network 108. Transfer process 135 further includesallowing first services responses 113 to be converted to second servicesresponses 114 (described below). The transfer module is accordingly alsoconfigured to convert a second data file format associated withoff-network payment network 108 to a first data file format associatedwith home payment network 102.

Off-network payment network 108 includes interface processor 140, anoff-network processor 147, and payment services computer system 107.Interface processor 140 is representative of a computing device capableof receiving second service request 109 from transfer process 135.Interface processor 140 is also capable of determining whether secondservice request 109 contains account identifiers associated with paymentcard services 106. Interface processor 140 is further capable ofcommunicating with payment services computer system 107 to register orapply payment services 106.

Payment services computer system 107 includes a payment servicesplatform 145, such as the MasterCard® in Control™ platform. MasterCard®in Control™ platform is a proprietary payment services platform createdby MasterCard International Incorporated® for providing cardholderservices associated with the exchange of financial transaction databetween financial institutions that are members of MasterCardInternational Incorporated®. (MasterCard is a registered trademark ofMasterCard International Incorporated located in Purchase, N.Y.).Payment services platform 145 is capable of communicating with interfaceprocessor 140 and registering an account to use payment services 106 orapplying payment services 106 associated with home payment network 102to payment transaction 104. Payment services computer system 107 alsoincludes off-network processor 147 which is capable of communicatingwith off-network issuer bank (not shown) and providing payment services106 to transactions initiated by an off-network cardholder (not shown).

In operation, cardholder 110 initially registers for payment services106 with issuer 120 using account registration 115. In the exampleembodiment, account registration 115 represents a web-based serviceallowing cardholder 110 to register for payment services 106 at aweb-site hosted by issuer 120. In the example embodiment, issuer 120transmits registration information to home network processor 112 whichconverts registration information using transfer process 135 to a formatthat may be received by interface processor 140. In alternativeembodiments, issuer 120 may convert registration information usingtransfer process 135 without using home network processor 112. In theexample embodiment, account registration 115 includes an accountidentifier (e.g., an account number) associated with the payment cardused for initiating transaction 104. The account identifier may be aprimary account number (PAN), a real card number (RCN), or any othertype of identifier that identifies or represents an account associatedwith payment card transaction 104.

Account registration 115 further includes payment services 106 to beassociated with the account identifier. In the example embodiment, alertnotifications service 150 may be associated with the account identifierassociated with payment transaction 104. Alert notifications service 150may be registered so that if payment transaction 104 exceeds a thresholdcurrency amount set in account registration 115, alerts will be sent. Inother words, when cardholder 110 registers with issuer 120 for paymentservices 106, cardholder 110 can register for alert notificationsservice 150 such that, when a transaction 104 exceeds a designatedamount, the payment services computer system 107 sends an alertnotification to cardholder 110 advising cardholder 110 of such event.

Account registration 115 also includes using transfer process 135 toconvert registration data to a format that can be used with paymentservices computer system 107. Transfer process 135 uses the translationmodule to convert registration data into a registration profile andtransmits the registration profile to payment services computer system107. Here, the translation module is used to convert a first data fileformat associated with home payment network 102 (e.g., registrationdata) to a second data file format associated with off-network paymentnetwork 108 (e.g., the registration profile).

Once cardholder 110 has registered 115 for payment services 106 and theregistration profile has been transmitted to interface processor 140 andsent to payment services computer system 107, payment services computersystem 107 is capable of providing payment services 106 when cardholder110 initiates payment transaction 104 over home payment network 102.

Cardholder 110 further initiates payment transaction 104 over homepayment network 104 with merchant 130 using a payment card. Paymenttransaction 104 includes an account identifier (e.g., a PAN) andtransaction details. Payment transaction 104 also includes paymenttransaction data. The payment transaction data may include, withoutlimitation, the time of payment transaction 104, the date of paymenttransaction 104, the amount of payment transaction 104, merchant 130associated with payment transaction 104, the category associated withmerchant 130 associated with payment transaction 104, the geographiclocation of payment transaction 104, and the purchase category (e.g.,food, clothing, or computers) of payment transaction 104.

Merchant 130 then sends an authorization request over home paymentnetwork 102 for payment transaction 104 to acquirer 125. Acquirer 125sends the authorization request along to issuer 120. In one embodiment,acquirer 125 transmits the authorization request to home networkprocessor 112 which determines whether the account associated withpayment transaction 104 is eligible for payment services 106. Inalternative embodiments, home network processor 112 sends theauthorization request to issuer 120 and issuer 120 determines whetherthe account associated with payment transaction 104 is eligible forpayment services 106. The entity that determines whether the accountassociated with payment transaction 104 is eligible for payment services106 is defined as a requestor and generates first service request 111.Determining whether the account is eligible for payment services 106 isrepresentative of determining whether cardholder 110 has registered theaccount identifier included in the authorization request with paymentservices 106. In the example embodiment, home network processor 112 willsearch a memory device (not shown) to determine if the accountidentifier is registered with issuer 120 for payment services 106. Inother embodiments, issuer 120 will search a memory device (not shown) todetermine if the account identifier is registered with issuer 120 forpayment services 106. In alternative embodiments, issuer 120 may send arequest to off-network payment network 108 to determine if the accountidentifier included in the authorization request is registered withpayment services 106.

If the account is eligible, the requestor (i.e., home network processor112 or issuer 120) will continue to process payment transaction 104, andwill generate first service request 111. First service request 111 isconverted, using transfer process 135, into second service request 109.Transfer process 135 uses the translation module to convert firstservice requests 111 to second service requests 109. The translationmodule ensures that second service requests 109 conform to identicalfile naming conventions, file header conventions, file structure andlayout conventions, file type conventions, and file size conventions. Inan alternative embodiment, first service requests 111 are convertedusing a translation module implementing XML-based transformationalmethods. In other embodiments, first service requests 111 may beconverted using translation modules implementing any transformationalmethod or language including, without limitation, Perl, AWK, TXL, or anyother method capable of converting first service requests 111 to applynames, headers, layouts, structures, file types, and file sizes requiredfor second service requests 109.

Second service request 109 is transmitted to and received by interfaceprocessor 140 which determines whether the account identifier associatedwith second service request 109 is registered for payment services 106.If the account identifier associated with second service request 109 isdetermined to be registered for payment services 106, interfaceprocessor 140 transmits second service request 109 to payment servicesplatform 145. Payment services platform 145 processes second servicerequest 109 by applying registered payment services 106 to secondservice request 109. Applying registered payment services 106 representsapplying at least one payment service 106 if second service request 109requires such application. Payment services 106 includes virtual cardmapping service 155, transaction rules and limits service 160, and alertnotifications service 150. Each payment service 106 is associated withrules and conditions for applying service 106. If payment service 106should be applied, payment services platform 145 generates firstservices response 113 based, at least in part, on payment services 106and payment transaction data associated with second service request 109.Payment services computer system 107 transmits first services response113 to interface processor 140. First services response 113 is then sentback to transfer process 135.

Here, transfer process 135 uses the translation module to facilitateconverting first services responses 113 into second services responses114. The translation module is now used to reverse the process describedwhen first service request 111 was converted to second service request109. The transfer module allows the a reversed conversion of firstservices responses 113 into second services responses 114 conforming toidentical file naming conventions, file header conventions, filestructure and layout conventions, file type conventions, and file sizeconventions associated with home payment network 102. In the exampleembodiment, first services responses 113 are converted using atranslation module implementing XML-based transformational methods. Inalternative embodiments, first services responses 113 may be convertedusing translation modules implementing any transformational method orlanguage including, without limitation, Perl, AWK, TXL, or any othermethod capable of converting first services responses 113 to applynames, headers, layouts, structures, file types, and file sizes requiredfor second services responses 114.

Second services response 114 is then transmitted back to the requestor(i.e., home network processor 112 or issuer 120) that sent first servicerequest 111 to transfer process 135. In the example embodiment, when therequestor is home network processor 112, the requestor will communicatewith acquirer 125 (e.g., return an authorization response denying acredit card transaction to merchant 130 based upon the application oftransaction rules and limits service 160) and/or cardholder 110 (e.g. toalert cardholder based upon the application of alert notificationsservice 150) depending on the contents of second services response 114.In alternative embodiments, when the requestor is issuer 120, therequestor will either act on the contents of second services response114 (e.g., instruct acquirer 125 to deny a credit card transaction basedupon the application of transaction rules and limits service 160) orcommunicate with cardholder 110 (e.g. to alert cardholder based upon theapplication of alert notifications service 150.)

Payment transaction 104 may be associated with an account identifierthat is registered for alert notifications service 150. In this example,payment transaction 104 is processed as described above and results inat least one of two outcomes. First, first services response 113 may begenerated and converted to second services response 114 resulting inalerting cardholder 110 that the payment card associated with cardholder110 has been used in payment transaction 104. Second, payment services106 may trigger an SMS (i.e., Short Message Service text messaging) oremail alert 165 sent directly from payment services computer system 107.

In the first example, cardholder 110 may use account registration 115which creates a registration profile on payment services computer system107. The registration profile may include information reflecting thatcardholder 110 would like to be notified by the requestor (i.e., homenetwork processor 112 or issuer 120) when the credit card balanceassociated with cardholder 110 exceeds a threshold of $3,000. Theregistration profile is therefore registered for alert notificationsservice 150 with this condition (i.e., alerts should be sent by therequestor when the credit card balance exceeds $3,000) applied. Paymenttransaction 104 is made for $500 using account identifiers correspondingto cardholder 110 with merchant 130. Prior to payment transaction 104,the credit card balance associated with cardholder 110 was $2,900.Payment transaction 104 results in first service request 111 beinggenerated by the requestor (i.e., home network processor 112 or issuer120). First service request 111 is converted using transfer process 135to second service request 109. Second service request 109 is received byinterface processor 140 which determines that the account identifierassociated with second service request 109 is registered for paymentservices 106 and transmits second service request 109 to paymentservices platform 145. Payment services platform 145 determines thatsecond service request 109 is associated with an account identifierwhich is registered for alert notifications service 150. Paymentservices platform 145 processes second service request 109 anddetermines that payment transaction data included indicates that secondservice request 109 is associated with payment transaction 104 which hasmoved the credit card balance associated with cardholder 110 to $3,400.Payment services platform 145 also determines alert notificationsservice 150 requires that the requestor (i.e., home network processor112 or issuer 120) must alert cardholder 110. Payment services platform145 generates first services response 113 including an instruction thatthe requestor send an alert to cardholder 110 in accordance with alertnotifications service 150. First services response 113 is converted tosecond services response 114 using transfer process 135. Second servicesresponse 114 is sent to the requestor. The requestor sends an electronicalert to a computing device associated with cardholder 110 indicatingthat the credit card balance associated with cardholder 110 has exceededthe threshold of $3,000.

In the second example, cardholder 110 also uses account registration 115and creates a registration profile on payment services computer system107. However, in this example, the registration profile may includeinformation reflecting that cardholder 110 would like to be notified bypayment services computer system 107 (rather than the requestor) whenthe credit card balance associated with cardholder 110 exceeds athreshold of $3,000. The registration profile is therefore registeredfor alert notifications service 150 with this condition (i.e., alertsshould be sent by payment services computer system 107 when the creditcard balance exceeds $3,000) applied. As in the first example, paymenttransaction 104 causes the credit card balance associated withcardholder to exceed $3,000. Again, payment transaction 104 results infirst service request 111 being generated by the requestor. Firstservice request 111 is again converted using transfer process 135 tosecond service request 109. Second service request 109 is received byinterface processor 140 which determines that the account identifierassociated with second service request 109 is registered for paymentservices 106 and transmits second service request 109 to paymentservices platform 145. Payment services platform 145 determines thatsecond service request 109 is associated with an account identifierwhich is registered for alert notifications service 150. However,payment services platform 145 determines that second service request 109is associated with an account identifier which is registered for SMS oremail alerts 165 from payment services computer system 107. In thiscase, in addition to generating an first services response 113(informing the requestor of the alert), payment services computer system107 sends an SMS text message directly to a computing device associatedwith cardholder 110. This option may be valuable for cardholders 110 whovalue speed or where the requestor lacks the ability to communicate withcardholder 110 electronically.

Payment transaction 104 may also be associated with an accountidentifier that is registered for virtual card mapping service 155. Inthis case cardholder 110 may use account registration 115 which createsa registration profile on payment services computer system 107. Theregistration profile may include information reflecting that cardholder110 would like to be able to use a virtual card number (VCN) inconjunction with payment transactions 104 wherein the VCN maps to a realcard number (RCN). The RCN directly represents the real numberassociated with, and typically printed on, a payment card. The VCN is asecondary number that only reflects the RCN based upon a mapping serviceprovided by virtual card mapping service 155. A VCN is issued with thepossibility of cardholder 110 deactivating it immediately withoutimpacting the underlying account and RCN. Accordingly, cardholder 110may find the use of VCNs and virtual card mapping service 155 desirablebecause it enables rapid fraud prevention and account control. This isbecause cardholder 110 can restrict the ability of a VCN to be usedwithout disabling or affecting the RCN.

In these cases, cardholder 110 may initiate payment transaction 104using a VCN. Payment transaction 104 results in first service request111 being generated by the requestor (i.e., home network processor 112or issuer 120). First service request 111 is converted using transferprocess 135 to second service request 109. Second service request 109 isreceived by interface processor 140 which determines that the accountidentifier is registered for payment services 106 and transmits secondservice request 109 to payment services platform 145. Payment servicesplatform 145 determines that second service request 109 is associatedwith an account identifier which is a VCN. Payment services platform 145identifies RCN associated with VCN by applying virtual card mappingservice 155. Payment services platform 145 processes second servicerequest 109 and determines whether RCN is associated with any additionalpayment services 106. Payment services platform 145 generates firstservices response 113 including instruction that issuer 120 use the RCNwith payment transaction 104. First services response 113 is convertedto second services response 114 using transfer process 135. Secondservices response 114 is sent to the requestor. In the exampleembodiment, when the home network processor 112 is the requestor, therequestor sends second services response 114 to issuer 120. In thealternative embodiment, where the requestor is issuer 120, the issuerimmediately receives second services response 114 after the transferprocess 135. In all embodiments, issuer 120 then processes paymenttransaction 104 using the RCN.

In some cases, payment services platform 145 may send first servicesresponse 113 without an initiating payment transaction 104. Firstservices response 113 is converted, using transfer process 135, tosecond services response 114. In these cases, payment services platform145 provides the requestor virtual card mapping data without an firstservice request 111 associated with payment transaction 104. Therequestor either transmits virtual card mapping data to issuer 120(where the requestor is home network processor 112) or the requestor isissuer 120 (i.e. issuer 120 has the virtual card mapping data). Issuer120 can store virtual card mapping data in its database. In these cases,issuer 120 may be able to convert a VCN for cardholder to an RCNimmediately without using off-network payment network 108. In suchcases, payment services platform 145 (and more generally, paymentservices computer system 107) provide virtual card mapping data toissuer to allow for rapid processing of payment transactions 104associated with a VCN (i.e., payment transactions 104 which areassociated with account identifiers registered to use virtual cardmapping service 155).

Payment services 106 also include transaction rules and limits service160. Cardholder 110 can register to have transaction rules and limitsservice 160 applied to payment transaction 104. In these embodiments,first services response 113 may be generated and converted to secondservices response 114 that may deny transactions that do not satisfytransaction rules and limits service 160. For example, cardholder 110may use account registration 115 which creates a registration profile onpayment services computer system 107. The registration profile mayinclude information reflecting that cardholder 110 would like to denyany payment transactions 104 which take place outside of New York, thehome state of cardholder 110, as a deterrent to fraud. The registrationprofile is therefore registered for transaction rules and limits service160 with this condition (i.e. all transactions must take place in NewYork) applied. Payment transaction 104 is made with account identifierscorresponding to cardholder 110 with merchant 130 in Ohio. Paymenttransaction 104 results in first service request 111 being generated bythe requestor (i.e., home network processor 112 or issuer 120). Firstservice request 111 is converted using transfer process 135 to secondservice request 109. Second service request 109 is received by interfaceprocessor 140 which determines that the account identifier associatedwith second service request 109 is registered for payment services 106and transmits second service request 109 to payment services platform145. Payment services platform 145 determines that second servicerequest 109 is associated with an account identifier which is registeredfor transaction rules and limits service 160. Payment services platform145 processes second service request 109 and determines that paymenttransaction data included indicates that second service request 109 isassociated with payment transaction 104 taking place in Ohio. Paymentservices platform 145 further determines that the account identifierassociated with second service request 109 is registered for transactionrules and limits service 160 and requires that all transactions musttake place in New York. Payment services platform 145 accordinglydetermines that payment transaction 104 should be denied for failing toadhere to the specified rule. Payment services platform 145 generatesfirst services response 113 including an instruction that issuer 120deny payment transaction 104 for violating conditions of transactionrules and limits service 160. In other examples, transaction rules andlimits service 160 may apply a similar process for customers specifyingrules including, without limitation, all payment transactions 104 mustbe associated with a certain category or categories (e.g., food,clothing, and gasoline), all payment transactions 104 must be for lessthan a maximum allowable spending limit, payment transactions 104 cannotbe more frequent than a given period (e.g., one transaction per day),payment transactions 104 cannot occur outside specific hours (e.g., nopurchase after midnight), and no payment transactions 104 can be for aprohibited category of purchase (e.g., no purchase of alcohol). Firstservices response 113 is sent to interface processor 140, converted tosecond services response 114 using transfer process 135 and sent to therequestor. The requestor either is issuer 120 or home network processor112. The requestor in either case instructs acquirer 125 to authorize ordeny the payment transaction 104 by sending an authorization response tomerchant 130.

FIG. 3 is a flowchart 200 illustrating an example method implemented bythe payment services computer system shown in FIG. 2 for processing ahome payment network payment transaction using off-network paymentservices. Cardholder 110 initiates 205 payment transaction 104 using anaccount identifier (e.g., a PAN). Acquirer 125 then processes paymenttransaction 104 for normal authorization and sends 210 paymenttransaction 104 to the requestor (i.e. home network processor 112 orissuer 120). In the example embodiment, where the requestor is homenetwork processor 112, acquirer 125 sends 210 payment transaction 104 tohome network processor 112. In alternative embodiments, issuer 120 isthe requestor and acquirer 125 sends 210 payment transaction 104 toissuer 120. The requestor (i.e. home network processor 112 or issuer120) then checks 215 if the account is within the account range eligiblefor payment services 106. If the account is not eligible, normalauthorization processing is performed 255 by issuer 120 and issuer 120returns 250 a normal authorization response to acquirer 125 and acquirer125 returns 265 the authorization response to merchant 130 andcardholder 110. If the account is eligible for payment services 106, therequestor (i.e. home network processor 112 or issuer 120) sends 220 aservice request message (i.e., second service request 109 converted fromfirst service request 111 using transfer process 135) to interfaceprocessor 140. Interface processor 140 sends (not shown) second servicerequest 109 to payment services platform 145. Payment services platform145 checks 225 second service request 109 to determine if the account iseligible for payment services 106. If the account is not eligible 230,normal authorization processing is performed 260 by issuer 120 andissuer 120 returns a normal authorization response 250 to acquirer 125and acquirer 125 returns 265 the authorization response to merchant 130and cardholder 110. If the account is eligible 230 for payment services106, payment services platform 145 processes second service request 109and generates 235 an first services response 113. Payment servicesresponse also provides 235 first services response 113 to interfaceprocessor 140. Interface processor 140 returns 240 off-network serviceresponse 113 to the requestor (i.e. home network processor 112 or issuer120). In returning 240 first services response 113, first servicesresponse 113 is converted to second services response 114 using transferprocess 135. Issuer 120 executes normal authorization with paymentservices 245. The requestor then returns 250 the authorization responseto acquirer 125 and acquirer 125 returns 265 the authorization responseto merchant 130 and cardholder 110.

FIG. 4 is a simplified block diagram of an example computer system 300representative of payment services platform 145 in payment processingenvironment 100 (both shown in FIG. 2). In the example embodiment,system 300 includes a server system 302 and a plurality of clientsubsystems, also referred to as client systems 304, connected to serversystem 302. In one embodiment, client systems 304 are computersincluding a web browser, such that server system 302 is accessible toclient systems 304 using the Internet. Client systems 304 areinterconnected to the Internet through many interfaces including anetwork, such as a local area network (LAN) and/or a wide area network(WAN), dial-in connections, cable modems, wireless-connections, andspecial high-speed ISDN lines. Client systems 304 may be any devicecapable of interconnecting to the Internet including a web-based phone,personal digital assistant (PDA), or other web-connectable equipment. Adatabase server 306 is connected to a database 308 containinginformation on a variety of matters, as described below in greaterdetail. In one embodiment, database 308 is stored on server system 302and may be accessed by potential users at one of client systems 304 bylogging onto server system 302 through one of client systems 304. In anyalternative embodiment, database 308 is stored remotely from serversystem 302 and may be non-centralized.

As discussed below, payment card information including account numbers,payment card numbers, expiration dates, and account statuses, such aswhether the account is open or closed, is stored within database 308.Further, data relating to the cardholder of a payment card may also bestored within database 308. Such cardholder data may include, forexample, cardholder name and cardholder billing address.

FIG. 5 is an expanded block diagram of an example embodiment of a serverarchitecture of system 400 in accordance with one embodiment of thepresent invention. Components in system 400, identical to components ofsystem 300 (shown in FIG. 4), are identified in FIG. 5 using the samereference numerals used in FIG. 4. System 400 includes server system 302and client systems 304. Server system 302 further includes databaseserver 306, an application server 402, a web server 404, a fax server406, a directory server 408, and a mail server 410. A disk storage unit412 is coupled to database server 306 and directory server 408. Servers306, 402, 404, 406, 408, and 410 are coupled in a local area network(LAN) 414. In addition, a system administrator's workstation 416, a userworkstation 418, and a supervisor's workstation 420 are coupled to LAN414. Alternatively, workstations 416, 418, and 420 are coupled to LAN414 using an Internet link or are connected through an Intranet.

Each workstation, 416, 418, and 420, is a personal computer having a webbrowser. Although the functions performed at the workstations typicallyare illustrated as being performed at respective workstations 416, 418,and 420, such functions can be performed at one of many personalcomputers coupled to LAN 414. Workstations 416, 418, and 420 areillustrated as being associated with separate functions only tofacilitate an understanding of the different types of functions that canbe performed by individuals having access to LAN 414.

Server system 302 is configured to be communicatively coupled to variousentities, including acquirers 422 and issuers 424, and to third parties,e.g., auditors, 434 using an Internet connection 426. Server system 302may also be communicatively coupled with a merchant 436. Thecommunication in the example embodiment is illustrated as beingperformed using the Internet, however, any other wide area network (WAN)type communication can be utilized in other embodiments, i.e., thesystems and processes are not limited to being practiced using theInternet. In addition, and rather than WAN 428, local area network 414could be used in place of WAN 428.

In the example embodiment, any authorized individual or entity having aworkstation 430 may access system 400. At least one of the clientsystems includes a manager workstation 432 located at a remote location.Workstations 430 and 432 include personal computers having a webbrowser. Also, workstations 430 and 432 are configured to communicatewith server system 302. Furthermore, fax server 406 communicates withremotely located client systems, including a client system 432, using atelephone link. Fax server 406 is configured to communicate with otherclient systems 416, 418, and 420 as well.

FIG. 6 illustrates an example configuration of a cardholder computerdevice 502 operated by a cardholder 501. Cardholder computer device 502may include, but is not limited to, client systems 304, 416, 418, and420, workstation 430, and manager workstation 432 (shown in FIG. 5).

Cardholder computer device 502 includes a processor 505 for executinginstructions. In some embodiments, executable instructions are stored ina memory area 510. Processor 505 may include one or more processingunits (e.g., in a multi-core configuration). Memory area 510 is anydevice allowing information such as executable instructions and/or otherdata to be stored and retrieved. Memory area 510 may include one or morecomputer readable media.

Cardholder computer device 502 also includes at least one media outputcomponent 515 for presenting information to cardholder 501. Media outputcomponent 515 is any component capable of conveying information tocardholder 501. In some embodiments, media output component 515 includesan output adapter such as a video adapter and/or an audio adapter. Anoutput adapter is operatively coupled to processor 505 and operativelycouplable to an output device such as a display device (e.g., a liquidcrystal display (LCD), organic light emitting diode (OLED) display,cathode ray tube (CRT), or “electronic ink” display) or an audio outputdevice (e.g., a speaker or headphones).

In some embodiments, cardholder computer device 502 includes an inputdevice 520 for receiving input from cardholder 501. Input device 520 mayinclude, for example, a keyboard, a pointing device, a mouse, a stylus,a touch sensitive panel (e.g., a touch pad or a touch screen), agyroscope, an accelerometer, a position detector, or an audio inputdevice. A single component such as a touch screen may function as bothan output device of media output component 515 and input device 520.

Cardholder computer device 502 may also include a communicationinterface 525, which is communicatively couplable to a remote devicesuch as server system 302 or a web server operated by a merchant.Communication interface 525 may include, for example, a wired orwireless network adapter or a wireless data transceiver for use with amobile phone network (e.g., Global System for Mobile communications(GSM), 3G, 4G or Bluetooth) or other mobile data network (e.g.,Worldwide Interoperability for Microwave Access (WIMAX)).

Stored in memory area 510 are, for example, computer readableinstructions for providing a user interface to cardholder 501 via mediaoutput component 515 and, optionally, receiving and processing inputfrom input device 520. A user interface may include, among otherpossibilities, a web browser and client application. Web browsers enablecardholders, such as cardholder 501, to display and interact with mediaand other information typically embedded on a web page or a website fromserver system 302 or a web server associated with a merchant. A clientapplication allows cardholder 501 to interact with a server applicationfrom server system 302 or a web server associated with a merchant.

FIG. 7 illustrates an example configuration of a server computer device675 such as server system 302 (shown in FIGS. 4 and 5). Server computerdevice 675 may include, but is not limited to, database server 306,application server 402, web server 404, fax server 406, directory server408, and mail server 410.

Server computer device 675 includes a processor 680 for executinginstructions. Instructions may be stored in a memory area 685, forexample. Processor 680 may include one or more processing units (e.g.,in a multi-core configuration).

Processor 680 is operatively coupled to a communication interface 690such that server computer device 675 is capable of communicating with aremote device such as cardholder computer device 502 or another servercomputer device 675. For example, communication interface 690 mayreceive requests from client systems 304 via the Internet, asillustrated in FIGS. 3 and 4.

Processor 680 may also be operatively coupled to a storage device 412.Storage device 412 is any computer-operated hardware suitable forstoring and/or retrieving data. In some embodiments, storage device 412is integrated in server computer device 675. For example, servercomputer device 675 may include one or more hard disk drives as storagedevice 412. In other embodiments, storage device 412 is external toserver computer device 675 and may be accessed by a plurality of servercomputer devices 675. For example, storage device 412 may includemultiple storage units such as hard disks or solid state disks in aredundant array of inexpensive disks (RAID) configuration. Storagedevice 412 may include a storage area network (SAN) and/or a networkattached storage (NAS) system.

In some embodiments, processor 680 is operatively coupled to storagedevice 412 via a storage interface 695. Storage interface 695 is anycomponent capable of providing processor 680 with access to storagedevice 412. Storage interface 695 may include, for example, an AdvancedTechnology Attachment (ATA) adapter, a Serial ATA (SATA) adapter, aSmall Computer System Interface (SCSI) adapter, a RAID controller, a SANadapter, a network adapter, and/or any component providing processor 680with access to storage device 412.

Memory areas 410 and 685 may include, but are not limited to, randomaccess memory (RAM) such as dynamic RAM (DRAM) or static RAM (SRAM),read-only memory (ROM), erasable programmable read-only memory (EPROM),electrically erasable programmable read-only memory (EEPROM), andnon-volatile RAM (NVRAM). The above memory types are example only, andare thus not limiting as to the types of memory usable for storage of acomputer program.

This written description uses examples to disclose the invention,including the best mode, and also to enable any person skilled in theart to practice the invention, including making and using any devices orsystems and performing any incorporated methods. The patentable scope ofthe invention is defined by the claims, and may include other examplesthat occur to those skilled in the art. Such other examples are intendedto be within the scope of the claims if they have structural elementsthat do not differ from the literal language of the claims, or if theyinclude equivalent structural elements with insubstantial differencesfrom the literal languages of the claims.

What is claimed is:
 1. A computer-implemented method for applyingpayment services to a payment transaction initiated by a cardholderusing a payment card over a first payment network, the payment servicesapplied using a payment services computer system hosted on a secondpayment network, the payment card issued to the cardholder by an issuerbank, said method comprising: receiving a service request at the paymentservices computer system from a requestor, the service request having afirst format that is readable by the second payment network, the servicerequest including payment transaction data; determining, at the paymentservices computer system, the payment services the service request isregistered to receive; processing the service request by applying theregistered payment services to the service request; generating, at thepayment services computer system, a services response based at least inpart on the registered payment services and the payment transactiondata; and transmitting the services response to at least one of thecardholder and the requestor.
 2. A computer-implemented method inaccordance with claim 1, wherein the requestor is at least one of theissuer bank, a home network processor, and a third party associated witheither the issuer bank or the home network processor.
 3. Acomputer-implemented method in accordance with claim 1, whereinreceiving a service request further comprises receiving a servicerequest from the requestor, wherein the service request is generated inresponse to the issuer bank receiving an authorization request messageassociated with the payment transaction.
 4. A computer-implementedmethod in accordance with claim 3, further comprising: providing atranslation module to the requestor; and using the translation module totranslate the authorization request message received by the requestorinto the service request having the first format such that the servicerequest is readable by the second payment network.
 5. Acomputer-implemented method in accordance with claim 1, whereinreceiving a service request further comprises receiving a servicerequest including an account identifier, the account identifieridentifying an account with the issuer bank that is associated with thepayment card and the cardholder.
 6. A computer-implemented method inaccordance with claim 5 wherein determining the payment services theservice request is registered to receive further comprises: comparingthe received account identifier to a plurality of registered accountidentifiers stored within a memory device coupled to the paymentservices computer system; confirming that the received accountidentifier is included in the plurality of registered accountidentifiers; and retrieving from the memory device the payment servicesthe registered account identifier is associated with.
 7. Acomputer-implemented method in accordance with claim 1 furthercomprising: receiving a registration profile at the payment servicescomputer system, the registration profile associated with at least oneof the cardholder and the payment card, the registration profileincluding an account identifier.
 8. A computer-implemented method inaccordance with claim 1, wherein generating a services responsecomprises: generating an instruction that the issuer bank authorize ordecline the payment transaction based upon authorization controls in theregistered payment services.
 9. A computer-implemented method inaccordance with claim 1, further comprising: receiving a service requestthat includes an account identifier; determining, at the paymentservices computer system, that the account identifier includes a virtualcard number; identifying a real card number corresponding to the virtualcard number; and processing the service request by applying theregistered payment services associated with the real card number to theservice request.
 10. A computer-implemented method in accordance withclaim 1, wherein transmitting the services response further comprises:transmitting an alert notification from the payment services computersystem to at least one of a computer device associated with thecardholder, and a computer device associated with the requestor, whereinthe alert notification is generated by applying the registered paymentservices to the payment transaction.
 11. Computer-readable storage mediafor applying payment services to a payment transaction initiated by acardholder using a payment card over a first payment network, thepayment services applied using a payment services computer system hostedon a second payment network, the payment card issued to the cardholderby an issuer bank, computer-readable storage media havingcomputer-executable instructions embodied thereon, wherein, whenexecuted by at least one processor associated with a computer devicecoupled to a memory device, the computer-executable instructions causethe processor to:receive a service request from a requestor, the servicerequest having a first format that is readable by the second paymentnetwork, the service request including payment transaction data;determine the payment services the service request is registered toreceive; process the service request by applying the registered paymentservices to the service request; generate, at the payment servicescomputer system, a services response based at least in part on theregistered payment services and the payment transaction data; andtransmit the services response to at least one of the cardholder and therequestor.
 12. The computer-readable storage media in accordance withclaim 11, wherein the requestor is at least one of the issuer bank, ahome network processor, and a third party associated with either theissuer bank or the home network processor.
 13. The computer-readablestorage media in accordance with claim 11, wherein thecomputer-executable instructions cause the processor to: receive aservice request from the requestor, wherein the service request isgenerated in response to the issuer bank receiving an authorizationrequest message associated with the payment transaction.
 14. Thecomputer-readable storage media in accordance with claim 13, wherein thecomputer-executable instructions cause the processor to: provide atranslation module to the requestor; and use the translation module totranslate the authorization request message received by the requestorinto the service request having the first format such that the servicerequest is readable by the second payment network.
 15. Thecomputer-readable storage media in accordance with claim 11, wherein thecomputer-executable instructions cause the processor to: receive aservice request including an account identifier, the account identifieridentifying an account with the issuer bank that is associated with thepayment card and the cardholder.
 16. The computer-readable storage mediain accordance with claim 15, wherein the computer-executableinstructions cause the processor to: compare the received accountidentifier to a plurality of registered account identifiers storedwithin a memory device coupled to the payment services computer system;confirm that the received account identifier is included in theplurality of registered account identifiers; and retrieve from thememory device the payment services the registered account identifier isassociated with.
 17. The computer-readable storage media in accordancewith claim 11, wherein the computer-executable instructions cause theprocessor to: receive a registration profile at the payment servicescomputer system, the registration profile associated with at least oneof the cardholder and the payment card, the registration profileincluding an account identifier.
 18. The computer-readable storage mediain accordance with claim 11, wherein the computer-executableinstructions cause the processor to: generate an instruction that theissuer bank authorize or decline the payment transaction based uponauthorization controls in the registered payment services.
 19. Thecomputer-readable storage media in accordance with claim 11, wherein thecomputer-executable instructions cause the processor to: receive aservice request that includes an account identifier; determine, at thepayment services computer system, that the account identifier includes avirtual card number; identify a real card number corresponding to thevirtual card number; and process the service request by applying theregistered payment services associated with the real card number to theservice request.
 20. The computer-readable storage media in accordancewith claim 11, wherein the computer-executable instructions cause theprocessor to: transmit an alert notification from the payment servicescomputer system to at least one of a computer device associated with thecardholder, and a computer device associated with the requestor, whereinthe alert notification is generated by applying the registered paymentservices to the payment transaction.
 21. A computer system for applyingpayment services to a payment transaction initiated by a cardholderusing a payment card over a first payment network, the payment servicesapplied using a payment services computer system hosted on a secondpayment network, the payment card issued to the cardholder by an issuerbank, the computer system comprising: a computing device including aprocessor; and a computer-readable storage device having encoded thereoncomputer-executable instructions that are executable by the processor toperform functions comprising: receiving a service request at the paymentservices computer system from a requestor, the service request having afirst format that is readable by the second payment network, the servicerequest including payment transaction data; determining the paymentservices the service request is registered to receive; processing theservice request by applying the registered payment services to theservice request; generating a services response based at least in parton the registered payment services and the payment transaction data; andtransmitting the services response to at least one of the cardholder andthe requestor.
 22. The computer system in accordance with claim 21,wherein the requestor is at least one of the issuer bank, a home networkprocessor, and a third party associated with either the issuer bank orthe home network processor.
 23. The computer system in accordance withclaim 21, wherein the computer-executable instructions are executable bythe processor to perform functions comprising: receiving a servicerequest from the requestor, wherein the service request is generated inresponse to the issuer bank receiving an authorization request messageassociated with the payment transaction.
 24. The computer system inaccordance with claim 23, wherein the computer-executable instructionsare executable by the processor to perform functions comprising:providing a translation module to the requestor; and using thetranslation module to translate the authorization request messagereceived by the requestor into the service request having the firstformat such that the service request is readable by the second paymentnetwork.
 25. The computer system in accordance with claim 21, whereinthe computer-executable instructions are executable by the processor toperform functions comprising: receiving a service request including anaccount identifier, the account identifier identifying an account withthe issuer bank that is associated with the payment card and thecardholder.
 26. The computer system in accordance with claim 25, whereinthe computer-executable instructions are executable by the processor toperform functions comprising: comparing the received account identifierto a plurality of registered account identifiers stored within a memorydevice coupled to the payment services computer system; confirming thatthe received account identifier is included in the plurality ofregistered account identifiers; and retrieving from the memory devicethe payment services the registered account identifier is associatedwith.
 27. The computer system in accordance with claim 21, wherein thecomputer-executable instructions are executable by the processor toperform functions comprising: receiving a registration profile at thepayment services computer system, the registration profile associatedwith at least one of the cardholder and the payment card, theregistration profile including an account identifier.
 28. The computersystem in accordance with claim 21, wherein the computer-executableinstructions are executable by the processor to perform functionscomprising: generating an instruction that the issuer bank authorize ordecline the payment transaction based upon authorization controls in theregistered payment services.
 29. The computer system in accordance withclaim 21, wherein the computer-executable instructions are executable bythe processor to perform functions comprising: receiving a servicerequest that includes an account identifier; determining, at the paymentservices computer system, that the account identifier includes a virtualcard number; identifying a real card number corresponding to the virtualcard number; and processing the service request by applying theregistered payment services associated with the real card number to theservice request.
 30. The computer system in accordance with claim 21,wherein the computer-executable instructions are executable by theprocessor to perform functions comprising: transmitting an alertnotification from the payment services computer system to at least oneof a computer device associated with the cardholder, and a computerdevice associated with the requestor, wherein the alert notification isgenerated by applying the registered payment services to the paymenttransaction.